Payment link

ABSTRACT

In one embodiment, an intended recipient of money transmits a payment link created by the recipient to an intended sender of money, where the link contains a locator to a site of a payment provider, information about the recipient (e.g., phone number), and the amount of money to be sent. The link can be sent via email, text, IM, or other means. The sender then accesses the link, such as by clicking or tapping on the link, which launches a checkout or payment page for the sender on the payment provider site. The sender completes the payment page, and the payment is sent to the recipient by the payment provider.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 14/268,621, filed May 2, 2014; issued as U.S. Pat. No. 9,292,838,which is a continuation application of U.S. application Ser. No.12/826,336, filed Jun. 29, 2010; issued as U.S. Pat. No. 8,719,156, bothof which are incorporated herein by reference in their entirety.

BACKGROUND

1. Field of the Invention

The present invention generally relates to on-line payments, and inparticular, to payments between two parties.

2. Related Art

More and more consumers are purchasing items and services overelectronic networks, such as the Internet. Consumers routinely searchfor and purchase products and services from merchants and individualsalike. The transactions can take place directly between an on-linemerchant or retailer and the consumer, where payment is typically madeby entering credit card or other financial information. Transactions canalso take place with the aid of an on-line payment provider, such asPayPal, Inc. of San Jose, Calif. Such payment providers can maketransactions easier and safer for the parties. Payment providers enablepayments to be made through many different convenient methods.

A payment to be made or received, such as after a purchase, a loanrepayment, a donation, a gift, etc., can be accomplished in manydifferent ways. Examples include a recipient issuing an invoice or asender initiating a check-out procedure or payment procedure. This canbe performed through a payment provider. However, obtaining payment froma sender may not always be prompt, due to many factors, including theinconvenience of the sender to make the payment. In one example, therecipient, which can be a merchant, seller, or anyone requesting money,sends a request to the sender for a payment. The request may be in theform of an electronic or paper invoice. Once received, the senderprocesses the invoice for payment, depending on the type of invoice.

For a paper invoice, the sender may review and then transmit paymentinformation, such as credit card information, bank information, or acheck. For an electronic invoice, the sender may need to enter recipientinformation and the sender's payment information in an electroniccommunication. This information may be cumbersome and time-consuming forthe sender, which may cause the sender to delay entering theinformation, resulting in a delayed payment to the recipient.

Thus, there is a need for a way that make it easier for senders to makea payment or send money to recipients without the disadvantages of theconventional methods above.

SUMMARY

In accordance with different embodiments, an intended recipient of moneytransmits a human-readable or user-discernable link created by therecipient to an intended sender of money, where the link contains alocator to a site of a payment provider, information about therecipient, and the amount of money to be sent. The human-readable oruser-discernable link is descriptive and in common language such thatnon-technical people can read the link and understand the meaning. Thesender then accesses the link, such as by clicking on the link, whichlaunches a checkout or payment page for the sender on the paymentprovider site. The sender completes the payment page, and the payment issent to the recipient by the payment provider.

In one embodiment, the link has the format ofhttp://[payment-provider_address]/[recipient_email]/[amount]. Therecipient can transmit the link to the sender in any number of ways,including as part of an email, text, instant message, paper, or anyother suitable medium. Clicking or going to the link launches a paymentpage from the payment provider site, which includes the recipient'sinformation and the amount to be paid obtained through the link. Thesender may then simply enter the sender's login information, such as auser name and password. Once verified, the sender views the recipientinformation and amount. If correct, the sender clicks on a button orlink to confirm the payment. The payment is then sent to the designatedrecipient.

In other embodiments, the link may have different formats. For example,the link may include a descriptor of what the payment is for, and/or therecipient information may be a mobile number or a username from a socialsite. Another example is a link that does not include the paymentamount. This allows the sender to enter in any suitable amount, whichmay be appropriate for soliciting charitable contributions. In differentembodiments, the link is easily understood by both the sender andrecipient, neither of which has to be technical and can both belayperson.

Using this method for payment provides numerous advantages. Therecipient has an easy and intuitive way to create a payment link fortransmitting to a sender. The sender has an easy to way make the paymentby simply clicking on the link and entering in a small amount ofreadily-available information. The sender does not even have to have anaccount with the payment provider. As a result, a recipient may receiveprompt payment due to the ease of which a sender can make the payment.

These and other features and advantages of the present invention will bemore readily apparent from the detailed description of the embodimentsset forth below taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart showing a payment process using a user-createdlink according to one embodiment;

FIG. 2 is a flowchart showing a process for payment provider in making apayment based on a user-created link, according to one embodiment;

FIGS. 3A-3F are exemplary formats of a user-created link according todifferent embodiments;

FIG. 4 is block diagram of a networked system suitable for implementingthe process of FIG. 1 in accordance with an embodiment of the invention;and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 4 according to one embodiment of thepresent disclosure.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

FIG. 1 is a flowchart 100 showing a process for a payment process usinga recipient-created link, according to one embodiment. At step 102, auser, which in this embodiment, is a recipient, creates a payment link.In other embodiments, the user can be a money sender or another party,such as a payment provider. The link includes, at a minimum, informationabout a payment provider facilitating the payment process andinformation about the recipient of the payment. The link may alsoinclude the amount of payment, currency, and/or a brief description,such as the subject matter of the payment. One example of a link ishttp://my.paypal.com/joe@ebay.com/10/lunch, although many differentformats and/or fields may be suitable. In this example, the paymentprovider is PayPal, Inc. of San Jose, Calif., the recipient'sinformation is an email address, the payment requested is $10 (defaultto dollars), and the payment is for lunch. Such links are easilyunderstood by non-technical individuals.

Once the payment link is created, the link is transmitted to a moneysender or payer at step 104. The transmission may be in any number ofways. For example, the user may send the link via a short messageservice (SMS) or text to the sender's mobile device. Because it isdesirable to reduce the length of the SMS, the additional subject fieldabove helps identify to the sender the purpose of the payment requestwithout the recipient having to enter additional information into theSMS. Other examples of suitable transmissions are email, paper, andinstant messaging (IM). With these, the sender may not need the subjectfield, as the sender can include the payment reason within the body ofthe transmission media. Depending on the transmission type, the link maybe sent electronically or by postal service, such as part of a paperinvoice or note.

After the link is transmitted and received by the sender, the senderaccesses the link at step 106. Access can be by clicking on or selectingthe link, copying and pasting the link into an Internet browser,re-typing the link into an Internet browser, or any other suitablemeans. For example, if the link is included in an SMS message, email, orIM message, the sender may simply tap on the link with a finger (on amobile device, such as an iPad or iPhone) or click on the link with amouse (on a PC) to access the link and open a new page based oninformation contained in the link. If the link was transmitted on paperor other non-electronic media, such that the link is not “live,” thesender can re-type the link into an Internet browser to open the pageassociated with the link.

When the link is accessed at step 106, the sender is directed to apayment page of the payment provider identified in the link. Otherinformation in the link may also be included, such as the recipient ofthe payment, the amount, and the subject of the payment. The paymentpage may request the user to enter certain information, including thepayment amount if not specified in the link. If the sender wishes tomake the requested payment to the user or recipient, the sender entersthe requested information at step 108.

The requested information may depend on whether the sender has anaccount with the payment provider. If the sender has an account, thesender may be requested to enter the sender's password and log into theaccount. The sender's email, username, or other identifier may beautomatically filled in based on information transmitted from thesender's device (e.g., mobile device or PC) or the sender may be askedto enter that information as well.

If the sender does not have an account, the sender may be requested toenter information required to make the payment through an acceptedfunding source. In one embodiment, the requested information includesone or more of the following: the sender's first name, last name,funding source account number (such as a credit card number or bankaccount number), type of funding source, expiration date of the fundingsource, security code of the funding source, and the sender's billingaddress. The sender may also have the option of creating an account withthe payment provider at the same time. In that case, the user may alsobe asked to provide a password and possibly a user name or otheridentifier.

The requested information above for the situation where the sender hasan account with the payment provider and when the sender does not havean account with the payment provider may be presented on the same pagewhen the sender access the payment link. For example, requested log ininformation may be on a right side of the page and requested fundingsource information may be on a left side of the page. This enables thesender to select a different funding source, even if the sender has anaccount with the payment provider.

After the appropriate information is entered at step 108, theinformation is processed by the payment provider. In one example, thepayment provider obtains account information of the recipient throughthe recipient's information contained in the link, e.g., the recipient'semail address. With this information, the payment provider is able totransfer funds into the recipient's account. The payment provider alsodetermines whether to approve payment from the sender, such as checkingwhether sufficient funds exist in the sender's designated funding sourceand the accuracy of the sender's entered information. If the payment isapproved, the payment provider transfers funds from the sender's fundingsource and credits the amount to the recipient's account. Thus, at step110, the recipient receives the requested amount.

FIG. 2 is a flowchart 200 showing a process for a payment provider inmaking a payment based on a user-created link, according to oneembodiment. At step 202, the payment provider, such as PayPal, Inc.,receives information from a payment link when a sender access the linkas discussed above. Information contained in the link about the paymentprovider is used to direct the communication to the payment providersite. Information contained in the link and received by the paymentprovider includes an identifier of a recipient, such as an emailaddress, and optionally a payment amount, currency, and the subject ofthe payment or other descriptor.

The payment provider also receives information about the sender, at step204. Note that sender information may be received at the same time thatthe link information is received at step 202, and thus, steps 202 and204 need not be sequential. The sender information can be obtained fromthe device used by the sender to access the payment link. For example,if the sender accesses the link through a PC, information from the PCassociated with the sender, such as the IP address or cookies, istransmitted to the payment provider. Similarly, if the sender access thelink through a smart phone, information, such as the phone number,associated with the sender is received by the payment provider. If, forsome reason, sender information is not received or the receivedinformation is not correct (such as if the sender is using anotherperson's computing device), the sender may correct that information onthe payment provider site.

Once the payment provider has received the sender information, adetermination is made, at step 206, whether the sender has an accountwith the payment provider. For example, using the sender information,such as a phone number or email address, the payment provider can checkwhether there is an associated account. If there is no account, thepayment provider requests the sender to enter information about afunding source at step 208. This may include selecting an acceptablefunding instrument, such as a type of credit card, a debit card, a bankaccount, etc., and filling out information such as account number,billing address, name, phone number, expiration date, security code,etc. for the selected funding instrument. The payment provider may alsoask the sender if the sender wants to open an account with the paymentprovider. If yes, the sender may then be requested to enter informationto create an account, such as a user name and password. The request foraccount creation and entering information can also be performed afterthe payment has been processed.

If, as determined at step 206, the sender has an account with thepayment provider, the payment provider asks the sender to enter log ininformation at step 210, such as a user name and password or otheraccount identifiers. The user name may already appear in the request ifthe payment provider can provide that through the received senderinformation. If the user name is not for the sender, such as if thesender is using another person's device to make the payment, the sendercan enter the sender's user name in the appropriate field.

After the requested information is entered at steps 208 or 210, thepayment provider processes the information at step 212. If theinformation was from step 208, the payment provider may verify that theentered information is associated with a valid funding instrument. Ifthe payment provider cannot authenticate the information, the paymentprovider may request the sender to re-enter all or part of theinformation or select another funding instrument. If the information wasfrom step 210, the payment provider may verify that the entered passwordmatches with the user name associated with the account. If not, thepayment provider may ask the sender to re-enter the password. In oneembodiment, when the payment provider cannot confirm the information,either from step 208 or 210, after a specific number of attempts, theprocess ends and the sender is notified to try again later. In otherembodiments, the sender is given an unlimited number of attempts toeither enter valid funding source information or valid log ininformation. If the payment amount was not part of the informationcontained in the link, the payment provider may request the sender entera payment amount and a currency type, e.g., U.S. dollars, Euros, etc.

Next, at step 214, a determination is made whether the recipient has anaccount with the payment provider. This can be made using the recipientinformation contained in the link received at step 202. In oneembodiment, the link contains an email address of the recipient, whichthe payment provider may use to determine whether an account existscorresponding to the email. If no account exists, the recipient may beasked to create an account, such as by the payment provider sending anotification to the recipient at the email address provided in thepayment link. The email may include a message that there is a paymentfor the recipient, and to collect the payment, the recipient needs tolog into the recipient's account with the payment provider or create anaccount with the payment provider.

If there is no account for the recipient, the recipient is asked tocreate an account in order to receive payment. In one embodiment, arequest is made to enter a user name and password, along with any otherneeded information such as name, address, phone number, email address,and financial instrument information (where funds can be transferredfrom or deposited into). The recipient may be asked to re-enter the username and password. If the requested information is accepted by thepayment provider, an account is created at step 216.

Once the recipient has an account with the payment provider, the paymentprovider processes the payment at step 218. For example, the paymentprovider debits the payment amount from the sender's account or selectedfunding source and credits the recipient's account with the paymentprovider. The recipient and/or the sender may be notified, such as byemail, that the payment has been processed.

In other embodiments, when the sender has been authenticated by thepayment provider, a notification is sent to the intended recipient thatthe recipient has a payment waiting. The notification, which may be sentvia email, text, or other means, can also include the payment amount andthe sender's name or other information. In order to retrieve thepayment, the recipient may be requested to log into the recipient'saccount with the payment provider, such as clicking or otherwiseselecting a link in the notification and entering a password andpossibly a user name. If the recipient does not have an account, thenotification may ask the recipient to create an account with the paymentprovider to retrieve the payment. Again, a link may be provided so thatthe recipient is directed to the payment provider site to enterrequested information for creating an account.

Thus, using the process described above, a recipient of money canquickly and easily create a payment link that is easily communicated toan intended sender of the money. This can be within a social or businesscontext. For example, two friends may be at a restaurant eating lunch,but one person does not have enough money or the ability to pay for hisportion of the meal or one person decides it is easier to pay withouthaving the server split the check. In this situation, the person paying(recipient) can create a payment link at any time and transmit the linkto the other person (sender) for payment of the other person's portionof the meal. The payment link can also be used by merchants to createinvoices for goods or services delivered but not yet paid for. Themerchant can then send the link, as an invoice, to the person whopurchased the goods or services for payment.

Using the payment link also allows the sender to quickly and easily makea payment. As discussed above, the sender can receive a payment requestinstantaneously and at any time through a delivery by email, text, IM,etc. The sender then just needs to access the link, which may be assimple as clicking or tapping the link to be directed to a payment pageof the payment provider. Next, the sender logs into the account andmakes the payment. Thus, the process may be as simple as clicking on alink and typing in a password.

Furthermore, as discussed above, the sender is not even required to havean account with the payment provider because other funding sources canbe used to make the payment.

FIGS. 3A-3F are exemplary formats of a user or recipient created paymentlink according to different embodiments. As discussed above, the paymentlink can include different fields and have different formats. FIG. 3Ashows a format with the payment provider site, the recipient email, andthe payment amount with currency type. Note that any type of dotcomaddress may be suitable, such as ones created by the payment providerspecifically for processing payment links. FIG. 3B is the same as thelink of FIG. 3A except for the addition of a payment subject, which is“lunch” in this example. Other examples of subjects may be a referencenumber to an invoice or an invoice number.

FIG. 3C shows a link similar to the one of FIG. 3A except that thecurrency type is not included. In such a situation, the payment providermay default to a standard currency, such as U.S. dollars. The defaultmay also be determined by the geographic location of the recipient,which the payment provider would have as part of the account informationof the recipient, or the geographic location of the sender, such asdetermined by the sender's account information or the billinginformation of the sender's funding source. The default currency may bechanged by the sender in some embodiments. Where a currency type isrequired, the payment provider may accept different formats, such asUS$50, 50USD, etc., to indicate the currency as U.S. dollars.

FIGS. 3D to 3F show links with recipient identifiers different than anemail address. FIG. 3D uses the recipient's phone number as therecipient identifier. FIG. 3E uses the recipient's Facebook™ name as therecipient identifier, and FIG. 3F uses the recipient's Twitter™ name asthe recipient identifier. Other types of identifiers may also besuitable, as long as they uniquely identify the recipient to the paymentprovider.

FIG. 4 is a block diagram of a networked system 400 configured to handlea financial transaction between a recipient and a sender, such asdescribed above, in accordance with an embodiment of the invention.System 400 includes a first user device 410, a second user device 462, amerchant server 440, and a payment service provider server 470 incommunication over a network 460. Payment service provider server 470may be maintained by a payment provider, such as PayPal, Inc. of SanJose, Calif. A first user 405, such as a sender person or merchant,utilizes first user device 410, and a second user 406, such as arecipient person or merchant, utilizes and second user device 462 forperforming a transaction with a payment provider.

First user device 410, second user device 462, merchant server 440, andpayment service provider server 470 may each include one or moreprocessors, memories, and other appropriate components for executinginstructions such as program code and/or data stored on one or morecomputer readable mediums to implement the various applications, data,and steps described herein. For example, such instructions may be storedin one or more computer readable media such as memories or data storagedevices internal and/or external to various components of system 400,and/or accessible over network 460.

Network 460 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 460 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks.

First user device 410 and second user device 462 may be implementedusing any appropriate hardware and software configured for wired and/orwireless communication over network 460. For example, in one embodiment,the two user devices may be implemented as a personal computer (PC), asmart phone, personal digital assistant (PDA), laptop computer, and/orother types of computing devices capable of transmitting and/orreceiving data, such as an iPad™ from Apple™.

First user device 410 may include one or more browser applications 415which may be used, for example, to provide a convenient interface topermit first user 405 to browse information available over network 460.For example, in one embodiment, browser application 415 may beimplemented as a web browser configured to view information availableover the Internet. First user device 410 may also include one or moretoolbar applications 420 which may be used, for example, to provideclient-side processing for performing desired tasks in response tooperations selected by first user 405. In one embodiment, toolbarapplication 420 may display a user interface in connection with browserapplication 415 as further described herein.

First user device 410 may further include other applications 425 as maybe desired in particular embodiments to provide desired features tofirst user device 410. For example, other applications 425 may includesecurity applications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 460, or othertypes of applications. Applications 425 may also include email, texting,voice and IM applications that allow first user 405 to send and receiveemails, calls, and texts through network 460, as well as create and/oraccess payment links as discussed above. First user device 410 includesone or more user identifiers 430 which may be implemented, for example,as operating system registry entries, cookies associated with browserapplication 415, identifiers associated with hardware of first userdevice 410, or other appropriate identifiers, such as used forpayment/user/device authentication. In one embodiment, user identifier430 may be used by a payment service provider to associate first user405 with a particular account maintained by the payment service provideras further described herein. A communications application 422, withassociated interfaces, enables first user device 410 to communicatewithin system 400.

Second user device 462 may have similar applications and modules asfirst user device 410, but is used, in this example, for creating andsending a payment link to request money from first user 405. Second userdevice 462 may also include one or more browser applications 415 and oneor more toolbar applications 420 which may be used, for example, toprovide a convenient interface to permit second user 406 to browseinformation and perform tasks over network 460. For example, in oneembodiment, browser application 415 may be implemented as a web browserconfigured to view information available over the Internet andcommunicate with merchant server 440 to receive and send informationabout purchases made through merchant server 440.

Second user device 462 may further include other applications 425 suchas security applications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 460, or othertypes of applications. Applications 425 may also include email, text,IM, and voice applications that allow second user 406 to communicatethrough network 460 and create and send payment links through network460. Second user device 462 includes one or more user identifiers 430which may be implemented, for example, as operating system registryentries, cookies associated with browser application 415, identifiersassociated with hardware of second user device 462, or other appropriateidentifiers, such as used for payment/user/device authentication, e.g.,the phone number associated with second user device 462. Identifiers maybe used by a payment service provider to associate second user 406 witha particular account maintained by the payment service provider.

Merchant server 440 may be maintained, for example, by an on-linemerchant offering various products and/or services in exchange forpayment to be received over network 460. Merchant server 440 includes adatabase 445 identifying available products and/or services (e.g.,collectively referred to as items) which may be made available forviewing and purchase by first user 405. Accordingly, merchant server 440also includes a marketplace application 450, which may be configured toserve information over network 460 to browser 415 of first user device410 and second user device 462. In one embodiment, first user 405 mayinteract with marketplace application 450 through browser applicationsover network 460 in order to view various products or servicesidentified in database 445.

Merchant server 440 also includes a checkout application 455 which maybe configured to facilitate the purchase by first user 405 of goods orservices identified by marketplace application 450. Checkout application455 may be configured to accept payment information from first user 405through payment service provider server 470 over network 460. Forexample, checkout application 455 may receive and process a paymentconfirmation from payment service provider server 470, as well astransmit transaction information to the payment provider and receiveinformation from the payment provider (e.g., a transaction ID). Checkoutapplication 455 may also enable payment through second user device 462in communication with the payment provider by using a payment link asdescribed herein.

Payment service provider server 470 may be maintained, for example, byan online payment service provider which may provide payment betweenfirst user 405, second user 406, and the operator of merchant server440. In this regard, payment service provider server 470 includes one ormore payment applications 475 which may be configured to interact withfirst user device 410, second user device 462, and/or merchant server440 over network 460 to facilitate the purchase of goods or services byfirst user 405 of first user device 410 or payment between first userdevice 410 and second user device 462.

Payment service provider server 470 also maintains a plurality of useraccounts 480, each of which may include account information 485associated with individual users. For example, account information 485may include private financial information of users of devices such asaccount numbers, passwords, device identifiers, user names, phonenumbers, credit card information, bank information, or other financialinformation which may be used to facilitate online transactions by firstuser 405. Advantageously, payment application 475 may be configured tointeract with merchant server 440 on behalf of first user 405 during atransaction with checkout application 455 to track and manage purchasesmade by users.

A transaction processing application 490, which may be part of paymentapplication 475 or separate, may be configured to receive informationfrom a user device and/or merchant server 440 for processing and storagein a payment database 495. Transaction processing application 490 mayinclude one or more applications to process information from a paymentlink and the sender of the payment link (e.g., first user 405) todetermine the recipient and sender of funds and the amount of funds tobe transferred. Other funding sources may also be processed through thisapplication. Payment application 475 may be further configured todetermine the existence of accounts for first user 405 and/or seconduser 406, as well as create new accounts if necessary.

Note that in different embodiments, system 400, merchant server 440 isnot needed, as first user device 410 and second user device 462 maycommunicate directly with each other and with payment service providerserver 470 to process payment requests and transfers between first user405 and second user 406. One example is if second user 406 lends moneyto first user 405, such as buying dinner for first user 405. Second userdevice 462 can then create and transmit a payment link to first userdevice 410, first user device 410 then access the link and communicateswith payment service provider server 470, which then processes thepayment request and effects a payment from first user 405 to second user406.

In the above embodiments, transmission and receipt of the payment linkis through electronic means. However, as discussed herein, the paymentlink can also be transmitted on paper through conventionalnon-electronic means, such as via the postal service or other deliveryservice. Thus, in these embodiments, the first user may receive thepayment link on a hard copy and then enter the payment link into firstuser device 410 to continue the payment process with payment serviceprovider server 470.

FIG. 5 is a block diagram of a computer system 500 suitable forimplementing one or more embodiments of the present disclosure. Invarious implementations, the user device may comprise a personalcomputing device (e.g., a personal computer, laptop, smart phone, PDA,Bluetooth device, key FOB, badge, etc.) capable of communicating withthe network. The merchant and/or payment provider may utilize a networkcomputing device (e.g., a network server) capable of communicating withthe network. It should be appreciated that each of the devices utilizedby users, merchants, and payment providers may be implemented ascomputer system 500 in a manner as follows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard (creating the payment link),selecting one or more buttons or links (accessing the payment link),etc., and sends a corresponding signal to bus 502. I/O component 504 mayalso include an output component, such as a display. An optional audioinput/output component 505 may also be included to allow a user to usevoice for inputting information by converting audio signals. Audio I/Ocomponent 505 may allow the user to hear audio. A transceiver 506transmits and receives signals between computer system 500 and otherdevices, such as another user device, a merchant server, or a paymentprovider server. In one embodiment, the transmission is wireless,although other transmission mediums and methods may also be suitable. Aprocessor 512, which can be a micro-controller, digital signal processor(DSP), or other processing component, processes these various signals,such as for display on computer system 500 or transmission to otherdevices via a communication link 518. Processor 512 may also controltransmission of information, such as cookies or IP addresses, to otherdevices.

Components of computer system 500 also include a system memory component514 (e.g., RAM) and a static storage component 516 (e.g., ROM). Computersystem 500 performs specific operations by processor 512 and othercomponents by executing one or more sequences of instructions containedin system memory component 514. Logic may be encoded in a computerreadable medium, which may refer to any medium that participates inproviding instructions to processor 512 for execution. Such a medium maytake many forms, including but not limited to, non-volatile media,volatile media, and transmission media. In various implementations,non-volatile media includes optical or magnetic disks, volatile mediaincludes dynamic memory, such as system memory component 514, andtransmission media includes coaxial cables, copper wire, and fiberoptics, including wires that comprise bus 502. In one example,transmission media may take the form of acoustic or light waves, such asthose generated during radio wave, optical, and infrared datacommunications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. For example, paymentlinks of different formats and fields have been described, but they arenot exhaustive. Depending on the payment provider, other syntax,formats, and/or fields may be used to create the payment link. Havingthus described embodiments of the present disclosure, persons ofordinary skill in the art will recognize that changes may be made inform and detail without departing from the scope of the presentdisclosure. Thus, the present disclosure is limited only by the claims.

What is claimed is:
 1. A system comprising: a non-transitory memorystoring instructions; and one or more hardware processors coupled to thenon-transitory memory and configured to read instructions from thenon-transitory memory to cause the system to perform operationscomprising: receiving an indication that a device is accessing a UniformResource Locator (URL) link, the URL link having been created based oninformation from a recipient and associated to a recipient account; inresponse to receiving the indication that the device is accessing theURL link, requesting sender account information from the device; and inresponse to receiving the sender account information, transferring anamount of funds from a sender account associated with the sender accountinformation to the recipient account.
 2. The system of claim 1, whereinthe operations further comprise: requesting, from the device, anumerical value in response to receiving the indication that the deviceis accessing the URL link; and in response to receiving the numericalvalue, setting the amount of funds to the numerical value.
 3. The systemof claim 1, wherein the operations further comprise creating the senderaccount based on the sender account information.
 4. The system of claim1, wherein the amount of funds is determined based at least in part ondata associated with the URL link.
 5. The system of claim 1, wherein theURL link comprises a currency symbol.
 6. The system of claim 1, whereinthe operations further comprise: receiving, from the device, anindication that a sender does not have an account with the system; inresponse to receiving the indication that the sender does not have anaccount with the system, requesting funding source information as atleast part of the sender account information.
 7. The system of claim 6,wherein the funding source information request comprises a billingaddress request.
 8. A method, comprising: receiving an indication that adevice is accessing a Uniform Resource Locator (URL) link, the URL linkcomprising an identifier of a receiver and an indication of an amount offunds designated by the receiver; in response to the indication that thedevice is accessing the URL link, transmitting to the device a requestfor authentication information; in response to receiving authenticationinformation from the device, determining a sender account based on theauthentication information; and in response to determining the senderaccount, transferring the amount of funds from the sender account to anaccount associated with the receiver.
 9. The method of claim 8, whereinthe authentication information comprises a second identifier associatedwith the sender account.
 10. The method of claim 9, wherein theauthentication information comprises a password associated with thesecond identifier.
 11. The method of claim 8, wherein the authenticationinformation comprises a payment card number.
 12. The method of claim 8,wherein the method further comprises creating the URL link based oninformation received from a recipient device.
 13. The method of claim 8,wherein the URL link includes a currency symbol.
 14. A systemcomprising: a non-transitory memory storing instructions; and one ormore hardware processors coupled to the non-transitory memory andconfigured to read instructions from the non-transitory memory to causethe system to perform operations comprising: in response to receiving afirst account information for a first account, associating an electroniclink address to a webpage, the first account information and theelectronic link address both comprising an identifier; directing a userdevice to the webpage in response to receiving, from the user device, anindication that the user device is attempting to access the electroniclink address; and transferring an amount from the first account to asecond account in response to receiving, from the user device throughthe webpage, second account information for the second account.
 15. Thesystem of claim 14, wherein the first account information comprises anemail address or a phone number.
 16. The system of claim 14, wherein theoperations further comprises: receiving, from the user device throughthe webpage, a numerical value; and in response to receiving thenumerical value, setting the amount to the numerical value.
 17. Thesystem of claim 14, wherein the second account information comprises apayment card number.
 18. The system of claim 14, wherein the firstaccount information comprises a payment card number.
 19. The system ofclaim 14, wherein the first account information comprises a firstpayment card number and the second account information comprises asecond payment card number.
 20. The system of claim 18 wherein thesecond account information comprises an identifier and password.